Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

Tagging subscribers to this area: @dotnet/area-system-reflection
See info in area-owners.md if you want to be subscribed.

@vitek-karas I tried updating MetadataUpdateHandlerAttribute but got compatibility errors with .net7.0.
Is introducing a breaking change intended ? if yes how to by pass the check ?

This is hitting the same problem as #84326 - just different attribute.
In this case it's a bit more subtle: For DynamicallyAccessedMembersAttribute it should be OK to reduce the annotation (in this case from All to "all methods only"). It should NOT be OK to broaden the annotation as that may introduce new warnings.

Do we have a way to baseline just one specific attribute difference - as intentional?

@ericstj @eerhardt

Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr, @marek-safar
See info in area-owners.md if you want to be subscribed.

In 7.0 we had

https://github.com/dotnet/runtime/blob/release/7.0/src/libraries/apicompat/ApiCompatBaseline.NetCoreAppLatestStable.txt

that allowed us to baseline specific known API compat issues. But I'm not seeing this in main. @ericstj, @ViktorHofer ?

It's the new format in Main: https://github.com/dotnet/runtime/blob/main/src/libraries/apicompat/ApiCompatBaseline.NetCoreAppLatestStable.xml

You could modify it directly, or try generating it.

To generate it you could do:

dotnet build ApiCompat.proj /p:ApiCompatGenerateSuppressionFile=true

@pedrobsaila thanks for this contribution.